Troubleshooting the GitLab agent for Kubernetes

2023-06-18 01:01| 来源: 网络整理| 查看: 265

Transport: Error while dialing failed to WebSocket dialValidationError(Deploymentadata)Error while dialing failed to WebSocket dial: failed to send handshake requestDecompressor is not installed for grpc-encodingCertificate signed by unknown authorityProject not foundFailed to perform vulnerability scan on workload: jobs.batch already existsInventory policy prevented actuation (strategy: Apply, status: Empty, policy: MustMatch)Parse error during installationTroubleshooting the GitLab agent for Kubernetes

When you are using the GitLab agent for Kubernetes, you might experience issues you need to troubleshoot.

You can start by viewing the service logs:

kubectl logs -f -l=app=gitlab-agent -n gitlab-agent

If you are a GitLab administrator, you can also view the GitLab agent server logs.

Transport: Error while dialing failed to WebSocket dial { "level": "warn", "time": "2020-11-04T10:14:39.368Z", "msg": "GetConfiguration failed", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing failed to WebSocket dial: failed to send handshake request: Get \\\"https://gitlab-kas:443/-/kubernetes-agent\\\": dial tcp: lookup gitlab-kas on 10.60.0.10:53: no such host\"" }

This error occurs when there are connectivity issues between the kas-address and your agent pod. To fix this issue, make sure the kas-address is accurate.

{ "level": "error", "time": "2021-06-25T21:15:45.335Z", "msg": "Reverse tunnel", "mod_name": "reverse_tunnel", "error": "Connect(): rpc error: code = Unavailable desc = connection error: desc= \"transport: Error while dialing failed to WebSocket dial: expected handshake response status code 101 but got 301\"" }

This error occurs when the kas-address doesn鈥檛 include a trailing slash. To fix this issue, make sure that the wss or ws URL ends with a trailing slash, like wss://GitLab.host.tld:443/-/kubernetes-agent/ or ws://GitLab.host.tld:80/-/kubernetes-agent/.

ValidationError(Deploymentadata) { "level": "info", "time": "2020-10-30T08:56:54.329Z", "msg": "Synced", "project_id": "root/kas-manifest001", "resource_key": "apps/Deployment/kas-test001/nginx-deployment", "sync_result": "error validating data: [ValidationError(Deploymentadata): unknown field \"replicas\" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta, ValidationError(Deploymentadata): unknown field \"selector\" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta, ValidationError(Deploymentadata): unknown field \"template\" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta]" }

This error occurs when a manifest file is malformed and Kubernetes can鈥檛 create the specified objects. Make sure that your manifest files are valid.

For additional troubleshooting, try to use the manifest files to create objects in Kubernetes directly.

Error while dialing failed to WebSocket dial: failed to send handshake request { "level": "warn", "time": "2020-10-30T09:50:51.173Z", "msg": "GetConfiguration failed", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing failed to WebSocket dial: failed to send handshake request: Get \\\"https://GitLabhost.tld:443/-/kubernetes-agent\\\": net/http: HTTP/1.x transport connection broken: malformed HTTP response \\\"\\\\x00\\\\x00\\\\x06\\\\x04\\\\x00\\\\x00\\\\x00\\\\x00\\\\x00\\\\x00\\\\x05\\\\x00\\\\x00@\\\\x00\\\"\"" }

This error occurs when you configured wss as kas-address on the agent side, but the agent server is not available at wss. To fix this issue, make sure the same schemes are configured on both sides.

Decompressor is not installed for grpc-encoding { "level": "warn", "time": "2020-11-05T05:25:46.916Z", "msg": "GetConfiguration.Recv failed", "error": "rpc error: code = Unimplemented desc = grpc: Decompressor is not installed for grpc-encoding \"gzip\"" }

This error occurs when the version of the agent is newer that the version of the agent server (KAS). To fix it, make sure that both agentk and the agent server are the same version.

Certificate signed by unknown authority { "level": "error", "time": "2021-02-25T07:22:37.158Z", "msg": "Reverse tunnel", "mod_name": "reverse_tunnel", "error": "Connect(): rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing failed to WebSocket dial: failed to send handshake request: Get \\\"https://GitLabhost.tld:443/-/kubernetes-agent/\\\": x509: certificate signed by unknown authority\"" }

This error occurs when your GitLab instance is using a certificate signed by an internal certificate authority that is unknown to the agent.

To fix this issue, you can present the CA certificate file to the agent by customizing the Helm installation. Add --set config.caCert="$(cat ~/path/to/ca.crt)" to the helm install command. Make sure to replace ~/path/to/ca.crt with the path to your internal CA鈥檚 certificate file. The file should be a valid PEM or DER-encoded certificate.

When you deploy agentk with a set config.caCert value, the certificate is added to configmap and the certificate file is mounted in /etc/ssl/certs.

$ kubectl get configmap -lapp=gitlab-agent -o yaml apiVersion: v1 items: - apiVersion: v1 data: ca.crt: |- -----BEGIN CERTIFICATE----- MIIFmzCCA4OgAwIBAgIUE+FvXfDpJ869UgJitjRX7HHT84cwDQYJKoZIhvcNAQEL ...truncated certificate... GHZCTQkbQyUwBWJOUyOxW1lro4hWqtP4xLj8Dpq1jfopH72h0qTGkX0XhFGiSaM= -----END CERTIFICATE----- kind: ConfigMap metadata: annotations: meta.helm.sh/release-name: self-signed meta.helm.sh/release-namespace: gitlab-agent-self-signed creationTimestamp: "2023-03-07T20:12:26Z" labels: app: gitlab-agent app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: gitlab-agent app.kubernetes.io/version: v15.9.0 helm.sh/chart: gitlab-agent-1.11.0 name: self-signed-gitlab-agent resourceVersion: "263184207" kind: List

You might see a similar error in the agent server (KAS) logs of your GitLab application server:

{"level":"error","time":"2023-03-07T20:19:48.151Z","msg":"AgentInfo()","grpc_service":"gitlab.agent.agent_configuration.rpc.AgentConfiguration","grpc_method":"GetConfiguration","error":"Get \"https://gitlab.example.com/api/v4/internal/kubernetes/agent_info\": x509: certificate signed by unknown authority"}

To fix it, install your internal CA鈥檚 public certificate in the /etc/gitlab/trusted-certs directory.

Alternatively, you can configure the agent server (KAS) to read the certificate from a custom directory. Add the following configuration to /etc/gitlab/gitlab.rb:

gitlab_kas['env'] = { 'SSL_CERT_DIR' => "/opt/gitlab/embedded/ssl/certs/" }

To apply the changes:

Reconfigure GitLab.

sudo gitlab-ctl reconfigure

Restart gitlab-kas.

gitlab-ctl restart gitlab-kas Project not found { "level ":"error ", "time ":"2022-01-05T15:18:11.331Z", "msg ":"GetObjectsToSynchronize.Recv failed ", "mod_name ":"gitops ", "error ":"rpc error: code = NotFound desc = project not found ", }

This error occurs when the project where you keep your manifests is not public. To fix it, make sure your project is public or your manifest files are stored in the repository where the agent is configured.

Failed to perform vulnerability scan on workload: jobs.batch already exists { "level": "error", "time": "2022-06-22T21:03:04.769Z", "msg": "Failed to perform vulnerability scan on workload", "mod_name": "starboard_vulnerability", "error": "running scan job: creating job: jobs.batch \"scan-vulnerabilityreport-b8d497769\" already exists" }

The GitLab agent performs vulnerability scans by creating a job to scan each workload. If a scan is interrupted, these jobs may be left behind and need to be cleaned up before more jobs can be run. You can clean up these jobs by running:

kubectl delete jobs -l app.kubernetes.io/managed-by=starboard -n gitlab-agent

We鈥檙e working on making the cleanup of these jobs more robust.

Inventory policy prevented actuation (strategy: Apply, status: Empty, policy: MustMatch) { "error":"inventory policy prevented actuation (strategy: Apply, status: Empty, policy: MustMatch)", "group":"networking.k8s.io", "kind":"Deployment", "name":"resource-name", "namespace":"namespace", "status":"Skipped", "timestamp":"2022-10-29T15:34:21Z", "type":"apply" }

This error occurs when the GitLab agent tries to update an object and the object doesn鈥檛 have the required annotations. To fix this error, you can:

Add the required annotations manually.Delete the object and let the agent recreate it.Change your inventory_policy setting.Parse error during installation

When you install the agent, you might encounter an error that states:

Error: parse error at (gitlab-agent/templates/observability-secret.yaml:1): unclosed action

This error is typically caused by an incompatible version of Helm. To resolve the issue, ensure that you are using a version of Helm compatible with your version of Kubernetes.

【本文地址】

公司简介

联系我们